Skip to content

Conversation

DerBaer0
Copy link

Before, methods would only be analysed (and mutants generated), if the a parameter shadows an instance variable. But a local variable can shadow an instance var as well.

And I'm not sure about the AssignmentExpression function. In my tests, it never had to change anything. Is it necessary?

Before, methods would only be analysed, if the a parameter shadows an instance variable. But a local variable can shadow an instance var as well.
@jeffoffutt
Copy link
Owner

DerBaer0, before my student and I check this request, can you be more clear?

  • Can you give an example scenario with a mutant that should be created that is not?
  • Can you identify yourself?

@DerBaer0
Copy link
Author

I use this simple Java program:
https://gist.github.com/DerBaer0/0aa400abf29bc2d5b897
muJava produces 1 JTD mutant: Line 18: this.value = this.bar; => this.value = bar;
I would expect more 3 mutants with the different "this.value"s replaced by "value".

I am a regular student, trying to use muJava for my thesis.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants